Quick-access menu for mobile device

ABSTRACT

A computing device displays a multi-button menu icon and a group of application icons associated with one of the buttons of the multi-button menu icon. User input is received to activate the multi-button menu icon and to identify a first button of the multi-button menu icon associated with a location of the user input. A group of application icons, associated with the identified first button of the multi-button menu icon, is displayed. A second button of the multi-button menu icon is identified based on a changed location of the user input, and a different group of application icons associated with the identified second button are displayed. The multi-button menu icon is deactivated upon removal of the user input, allowing one of the application icons to be selected with a second user input.

BACKGROUND

Mobile devices (e.g., cell phones, personal digital assistants (PDAs),etc.) are being configured to support an increasing amount and varietyof applications. For example, a mobile device may include telephoneapplications, organizers, email applications, instant messaging (IM)applications, games, cameras, image viewers, etc. Users typically maylaunch an application by selecting an icon (or shortcut) to activate theapplication. Despite the large number of options, users still desire tofind and select a desired icon quickly. However, the available displaysize may limit the number of icons that can be effectively presented dueto the size of the device containing the display. Existing userinterfaces may provide one of a variety of menu formats that group menuitems into categories and sub-categories. These user interfaces mayrequire a user to “drill down” through multiple menus to select adesired icon or other item.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram illustrating an exemplary implementation of theconcepts described herein;

FIG. 2 depicts a diagram of an exemplary device in which systems and/ormethods described herein may be implemented;

FIG. 3 depicts a diagram of exemplary components of the deviceillustrated in FIG. 2;

FIG. 4 depicts a diagram of exemplary functional components of thedevice illustrated in FIG. 2;

FIGS. 5A and 5B provide examples of a quick-access menu arrangementaccording to implementations described herein;

FIGS. 6A and 6B illustrate exemplary menu operations capable of beingperformed by the device depicted in FIG. 2;

FIG. 7 depicts a flow chart of an exemplary process for providing aquick-access menu according to implementations described herein;

FIG. 8 provides an illustration of an exemplary implementation of aquick-access menu on a mobile device;

FIG. 9 provides an illustration of another exemplary implementation of aquick-access menu on a mobile device; and

FIG. 10 provides an illustration of still another exemplaryimplementation of a quick-access menu on a mobile device.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The following detailed description refers to the accompanying drawings.The same reference numbers in different drawings may identify the sameor similar elements. Also, the following detailed description does notlimit the invention.

Systems and/or methods described herein may provide a quick-access menusystem for a mobile device (e.g., a cell phone, a PDA, a personalcomputer, a laptop computer, a remote control, etc.). In oneimplementation, the quick-access menu arrangement may include amulti-button menu icon. Each button of the multi-button menu icon may beassociated with a unique group of application icons that can bedisplayed around the multi-button menu icon on a screen of the mobiledevice. User input, such as a touch on a touch-sensitive screen, may beapplied to the multi-button menu icon to activate the quick-access menusystem. The user input may move over the different buttons in themulti-button menu icon and the mobile device may interchangeably displaygroups of application icons based on the button currently associatedwith the user input.

The term “application icon,” as used herein, may refer to any imagepresented on a screen of a device that, when selected by a user,provides access to a specific file, directory, window, option, program,or application. Each application icon may be associated with executableapplications capable of being executed by the mobile device.

FIG. 1 provides a diagram illustrating an exemplary implementation of aquick-access menu arrangement 100. Quick-access menu arrangement 100 mayinclude a multi-button menu icon 110 that includes multiple quick-accessbuttons 120 (referred to herein collectively as “quick-access buttons120,” and individually as “quick-access button 120”). Each ofquick-access buttons 120 may be associated with a group of applicationicons 130-1 through 130-N (referred to herein collectively as“application icons 130,” and individually as “application icon 130”). Anindicator 140 may identify to a user the particular quick-access buttonthat is currently selected.

In implementations described herein, the user may activate themulti-button menu icon 110, select a quick-access button 120 that willautomatically display a group of application icons 130, and then selectan application icon 130 from the displayed group of application icons130. In the exemplary implementation of a touch-sensitive interface, auser may select multi-button menu icon 110 with a touch (e.g., the touchof a finger, stylus, etc.) and then slide the touch over the variousquick-access buttons 120 to switch the viewable group of applicationicons 130. Removal of the user's touch from the multi-button menu icon110 may deactivate multi-button menu icon 110 and allow the user toselect (e.g., with another touch) an application icon 130 from thecurrently displayed group of application icons 130.

In an exemplary implementation, as shown in FIG. 1, quick-access menuarrangement 100 may include a multi-button menu icon 110 having ninequick-access buttons 120 in a three-by-three arrangement. For eachquick-access button 120, quick-access menu arrangement 100 may displayeleven application icons 130. Thus, in the configuration of FIG. 1,ninety-nine application icons 130 may be made available to the user withas few as two user-input commands (e.g., two touches).

Although FIG. 1 shows an exemplary quick-access menu arrangement 100, inother implementations, quick-access menu arrangement 100 may containfewer, different, differently arranged, or additional icons thandepicted in FIG. 1. For example, multi-button menu icon 110 may includea different number and/or arrangement of quick-access buttons 120. Also,quick-access menu arrangement 100 may include a different number and/orarrangement of application icons 130 associated with each quick-accessbutton 120. Furthermore, multi-button menu icon 110 may be positioned ina different location within quick-access menu arrangement 100, such as,for example, a location selected by a user.

FIG. 2 is a diagram of an exemplary device 200 in which systems and/ormethods described herein may be implemented. Device 200 may includeradiotelephone, a personal communications system (PCS) terminal (e.g.,that may combine a cellular radiotelephone with data processing and datacommunications capabilities), a PDA (e.g., that can include aradiotelephone, a pager, Internet/intranet access, etc.), a remotecontrol (e.g., for a television), a portable gaming system, a globalpositioning system (GPS) device, a printer, a facsimile machine, apager, a camera (e.g., a contemporary camera or a digital camera), avideo camera (e.g., a camcorder), a calculator, binoculars, a telescope,a personal computer, a laptop computer, any other device capable ofutilizing a touch screen display, a thread or process running on one ofthese devices, and/or an object executed by one of these devices.

As illustrated in FIG. 2, device 200 may include a housing 210, aspeaker 220, a display 230, control buttons 240, and/or a microphone250. Housing 210 may protect the components of device 200 from outsideelements. Housing 210 may include a structure configured to hold devicesand components used in device 200, and may be formed from a variety ofmaterials. For example, housing 210 may be formed from plastic, metal,or a composite, and may be configured to support speaker 220, display230, control buttons 240 and/or microphone 250.

Speaker 220 may provide audible information to a user of device 200.Speaker 220 may be located in an upper portion of device 200, and mayfunction as an ear piece when a user is engaged in a communicationsession using device 200. Speaker 220 may also function as an outputdevice for music and/or audio information associated with games and/orvideo images played on device 200.

Display 230 may provide visual information to the user. For example,display 230 may display text input into device 100, text, images, video,and/or graphics received from another device, and/or informationregarding incoming or outgoing calls or text messages, emails, media,games, phone books, address books, the current time, etc. For example,screen 310 may include a liquid crystal display (LCD), such as a thinfilm transistor (TFT) LCD, etc.

In one implementation, display 230 may include a touch screen displaythat may be configured to receive a user input when the user touches (orcomes in close proximity to) display 230. For example, the user mayprovide an input to display 230 directly, such as via the user's finger,or via other devices, such as a stylus. User inputs received via display230 may be processed by components and/or devices operating in device200. The touch-screen-enabled display 230 may permit the user tointeract with device 200 in order to cause device 200 to perform one ormore operations. Exemplary technologies to implement a touch screen ondisplay 230 may include, for example, a near-field-sensitive (e.g.,capacitive) overlay, an acoustically-sensitive (e.g., surface acousticwave) overlay, a photo-sensitive (e.g., infra-red) overlay, a pressuresensitive (e.g., resistive and/or capacitive) overlay, and/or any othertype of touch panel overlay that allows display 230 to be used as aninput device. The touch-screen-enabled display 230 may also include theability to identify movement of a body part or a pointing device as itmoves on or near the surface of the touch-screen-enabled display 230.

Control buttons 240 may permit the user to interact with device 200 tocause device 200 to perform one or more operations. For example, controlbuttons 240 may be used to cause device 200 to transmit information.Microphone 250 may receive audible information from the user. Forexample, microphone 250 may receive audio signals from the user and mayoutput electrical signals corresponding to the received audio signals.

Although FIG. 2 shows exemplary components of device 200, in otherimplementations, device 200 may contain fewer, different, differentlyarranged, or additional components than depicted in FIG. 2. For example,in some implementations device 200 may include a keypad, such as astandard telephone keypad, a QWERTY-like keypad (e.g., a traditionalconfiguration of typewriter or computer keyboard keys), or anotherkeypad layout. In still other implementations, a component of device 200may perform one or more tasks described as being performed by anothercomponent of user device 200.

FIG. 3 is a diagram of exemplary components of device 200. Asillustrated, device 200 may include a processor 300, a memory 310, auser interface 320, a communication interface 330, and/or an antennaassembly 340.

Processor 300 may include one or more microprocessors, applicationspecific integrated circuits (ASICs), field programmable gate arrays(FPGAs), or the like. Processor 300 may control operation of device 200and its components. In one implementation, processor 300 may controloperation of components of device 200 in a manner described herein.

Memory 310 may include a random access memory (RAM), a read-only memory(ROM), and/or another type of memory to store data and instructions thatmay be used by processor 300. In one implementation, memory 310 maystore data used to display a graphical user interface, such asquick-access menu arrangement 100 on display 230.

User interface 320 may include mechanisms for inputting information todevice 200 and/or for outputting information from device 200. Examplesof input and output mechanisms might include buttons (e.g., controlbuttons 240, keys of a keypad, a joystick, etc.); a speaker (e.g.,speaker 220) to receive electrical signals and output audio signals; amicrophone (e.g., microphone 250) to receive audio signals and outputelectrical signals; a display (e.g., display 230) to receive touch inputand/or to output visual information (e.g., time-related items receivedby device 200); a vibrator to cause device 200 to vibrate; and/or acamera to receive video and/or images.

Communication interface 330 may include, for example, a transmitter thatmay convert baseband signals from processor 300 to radio frequency (RF)signals and/or a receiver that may convert RF signals to basebandsignals. Alternatively, communication interface 330 may include atransceiver to perform functions of both a transmitter and a receiver.Communication interface 330 may connect to antenna assembly 340 fortransmission and/or reception of the RF signals.

Antenna assembly 340 may include one or more antennas to transmit and/orreceive RF signals over the air. Antenna assembly 340 may, for example,receive RF signals from communication interface 330 and transmit themover the air, and receive RF signals over the air and provide them tocommunication interface 330. In one implementation, for example,communication interface 330 may communicate with a network and/ordevices connected to a network.

As will be described in detail below, device 200 may perform certainoperations described herein in response to processor 300 executingsoftware instructions of an application contained in a computer-readablemedium, such as memory 310. A computer-readable medium may be defined asa physical or logical memory device. A logical memory device may includea space within a single physical memory device or spread across multiplephysical memory devices. The software instructions may be read intomemory 310 from another computer-readable medium or from another devicevia communication interface 330. The software instructions contained inmemory 310 may cause processor 300 to perform processes that will bedescribed later. Alternatively, hardwired circuitry may be used in placeof or in combination with software instructions to implement processesdescribed herein. Thus, implementations described herein are not limitedto any specific combination of hardware circuitry and software.

Although FIG. 3 shows exemplary components of device 200, in otherimplementations, device 200 may contain fewer, different, differentlyarranged, or additional components than depicted in FIG. 3. In stillother implementations, a component of device 200 may perform one or moreother tasks described as being performed by another component of device200.

FIG. 4 provides a diagram of exemplary functional components of device200. As shown in FIG. 4, device 200 may include a menu controller 410and menu data 420. Device 200 may also include other peripheralapplications (not shown) associated with one or more application icons130. Peripheral applications may include, for example, a telephoneapplication, a text-messaging application, an email application, aninstant messaging (IM) application, a calendar application, a multimediamessaging service (MMS) application, a short message service (SMS)application, an image viewing application, a camera application, anorganizer, a video player, an audio application, a GPS application, etc.

Menu controller 410 may generate and update a graphical user interfacefor a quick-access menu arrangement (e.g., quick-access menu arrangement100). In one implementation, menu controller 410 may assembleapplication icons 130 based on one or more templates. Templates mayinclude for example, arrangements for groups of application icons 130associated with each quick-access button 120 of multi-button menu icon110. For example, menu controller 410 may retrieve, from menu data 420,an application icon 130 representing a peripheral application, applystored user preferences, and insert the application icons 130 into agraphic template.

Menu controller 410 may receive input to identify what application icons130 may be assigned to a particular group associated with a quick-accessbutton 120. Menu controller 410 may store group assignments, forexample, in menu data 420. Menu controller 410 may also store triggerinformation to detect when multi-button menu icon 110 isactivated/deactivated. Menu controller 410 may also include logic topresent multi-button menu icon 110 in an activated or deactivated mode.When multi-button menu icon 110 is in an activated mode, menu controller410 may track user input to the multi-button menu icon 110 and display agroup application icons 130 corresponding to the currently selectedquick-access button 120 of multi-button menu icon 110.

Menu data 420 may include information that may be used by menucontroller 410 to compile the quick-access menu arrangement. Menu data420 may include, for example, menu templates, application icons, icongroupings, menu triggers, and/or configurations for the multi-buttonmenu icon, and user preferences. User preferences may include, forexample, format preferences for the quick-access menu arrangement, suchas font/icon sizes, icon group definitions, group menu titles, theposition of multi-button icon 110, and/or transition animations forswitching between icon groups (e.g., slide in/out, wipe orientations,scattering, etc.). In some implementations, groups of application icons(e.g., the particular application icons associated with eachquick-access button 120) may be entirely user-configurable. In otherimplementations, the groups of application icons may include acombination of default icons and user-selected icons.

Although FIG. 4 shows exemplary functional components of device 200, inother implementations, device 200 may contain fewer, different,differently arranged, or additional functional components than depictedin FIG. 4. In still other implementations, a functional component ofdevice 200 may perform one or more tasks described as being performed byanother functional component of device 200.

FIGS. 5A and 5B provide examples of quick-access menu arrangement 100according to implementations described herein. FIG. 5A provides apartial view of quick-access menu arrangement 100 with multi-button menuicon 110 in an inactive state. FIG. 5B provides a partial view ofquick-access menu arrangement 100 with multi-button menu icon 110 in anactive state.

As shown in FIG. 5A, in an inactive state, multi-button menu icon 110may be displayed at a comparatively small size (relative to the size ofdisplay 230). Indicator 140 may be shown to identify the currentlyselected quick-access button 120 to which the displayed applicationicons correspond. Thus, in FIG. 5A, the application icons (e.g.,applications 130-7, 130-8, 130-9, 130-10, and 130-11), associated withthe quick-access button 120 at the lower-right right of multi-buttonmenu icon 110, are displayed.

In one implementation, as shown in FIG. 5B, a user may activatemulti-button menu icon 110 by, for example, a touch 500 on atouch-sensitive display in the area of multi-button menu icon 110. Inother implementations, multi-button menu icon 110 may be activated byother mechanisms, such as a touch on a touchpad, a press of a designatedcontrol button (e.g., one of control buttons 240), a press on apressure-sensitive display, and/or a selection using a cursor. As shownin the exemplary implementation of FIG. 5B, activation of multi-buttonmenu icon 110 may cause device 100 to enlarge and/or alter theappearance of multi-button menu icon 110. Additionally and/oralternatively, individual quick-access buttons 120 may be enlargedand/or altered as the user's touch (or cursor) slides over eachquick-access button 120. Additionally and/or alternatively, labels orimages (e.g., “1,” “2,” . . . “9”) may be displayed on individualquick-access buttons 120. Furthermore, the size and appearance ofindicator 140 may also be enlarged and/or altered to indicate thecurrently selected quick-access button 120. Thus, as shown in FIG. 5B,touch 500 at quick-access button 120 “2” may simultaneously cause theactivation of multi-button menu icon 110, the enlargement ofmulti-button menu icon 110, and the display of the application icons 130associated with quick-access button 120 “2.”

FIGS. 6A and 6B illustrate exemplary menu operations capable of beingperformed by a device, such as device 200. In FIGS. 6A and 6B,quick-access menu arrangement 100 is shown as a function of timeprogressing from time t₀ to time t₃. FIG. 6A provides a view ofquick-access menu arrangement 100 times t₀ and t₁. At time t₀,multi-button menu icon 110 may be in an inactive state. Indicator 140may be shown on the center quick-access button of multi-button menu icon110 and a group of application icons 130 corresponding to the currentlyselected quick-access button may be displayed. At time t₁, a user mayapply a touch 600 generally to the center of multi-button menu icon 110to activate multi-button menu icon 110. Multi-button menu icon 110 maybe enlarged. Because touch 600 is applied generally over the currentlocation of indicator 140, the group of application icons 130 may remainunchanged.

FIG. 6B provides a view of quick-access menu arrangement 100 at times t₂and t₃, subsequent to times t₀ and t₁, of FIG. 6A. At time t₂, touch 600may slide to the right-center of multi-button menu icon 110 whilemulti-button menu icon 110 remains in an active state. Indicator 140 maybe shown on the right-center quick-access button of multi-button menuicon 110 and a different group of application icons 130 corresponding tothe currently selected quick-access button may be displayed. At time t₃,the user may have removed touch 600 from multi-button menu icon 110,which may deactivate multi-button menu icon 110. Multi-button menu icon110 may be reduced to the inactive size and indicator 140 may remaindisplayed on the quick-access button corresponding to the last toucharea of the user. In other implementations, multi-button menu icon 110may be deactivated using another gesture, such a tap or press on adisplay 230. A second touch 601 may be applied by the user to select aparticular application icon 130 from the group of application icons 130associated with the currently selected quick-access button.

FIG. 7 depicts a flow chart of an exemplary process 700 providing aquick-access menu according to implementations described herein. In oneimplementation, process 700 may be performed by device 200.

As illustrated in FIG. 7, process 700 may begin with detecting a userinput to a multi-button menu icon of the device (block 710) andenlarging the multi-button menu icon (block 720). For example, in oneimplementation, device 200 (e.g., menu controller 410) may identifytouch on a touch-sensitive display that corresponds to the location of amulti-button menu icon (e.g., multi-button menu icon 110). Themulti-button menu icon 110 may include, for example, multiplequick-access buttons (e.g., quick-access buttons 120), where eachquick-access button can be associated with a group of application icons(e.g. application icons 130). In another exemplary implementation,device 200 may detect user input for the multi-button menu icon via acursor guided by a mouse, touch panel, or other cursor-based user-inputdevice. In still another exemplary implementation, device 200 may detectuser input for the multi-button menu icon from a menu selection ordedicated control button (e.g., one of control buttons 240). In responseto the user input, device 200 may enlarge the multi-button menu icon110. In one implementation, the multi-button menu icon may besufficiently enlarged, for example, to more easily accommodate a touchon the touch-sensitive display. In other implementations, themulti-button menu icon may be enlarged or otherwise altered to indicatethat the multi-button menu icon is in an active state. In someimplementations, enlargement of the multi-button menu icon may beoptional.

A quick-access button associated with the location of the user input maybe identified (block 730). For example, device 200 may identify aparticular quick-access button (e.g., one of quick-access buttons 120)associated with the location of the touch on the multi-button menu icon.In another exemplary implementation, device 200 may identify aparticular quick-access button associated with the location of thecursor (guided, e.g., by the mouse, touch-panel, or other input device)on the multi-button menu icon. In still another exemplaryimplementation, device 200 may identify a particular quick-access buttonbased on the direction from a keypad or control button, such as anarrow, trackball, or joystick.

Items associated with the identified quick-access button may bedisplayed on the device screen (block 740). For example, device 200 maydisplay a group of application icons (e.g. application icons 130)associated with the quick-access button identified based on the touchlocation, the cursor location, or the control button direction. Thegroup of application icons may be, for example, previously configuredgroups determined by the user or default groups set by, for example, anoriginal equipment manufacturer (OEM) or software provider.

It may be determined if the location of the user input changes (block750). For example, device 200 may identify a change in the touchlocation, the cursor location, or the control button direction whilemulti-button menu icon 110 remains active. If it is determined that thelocation of the user input has changed (block 750—YES), then process 700may return to block 730 to identify a different quick-access button anddisplay a group of application icons associated with the differentquick-access button.

If it is determined that the location of the user input has not changed(block 750—NO), deactivation of the multi-button menu icon may bedetected (block 760) and the multi-button menu icon may be restored toits original size (block 770). For example, device 200 may eventuallydetect removal of the user input from the multi-button menu icon.Removal of the user input may include, for example, removal of the touchfrom the touch sensitive display, release of a mouse-click associatedwith a cursor, or pressing of a dedicated control button. In responsethe detected deactivation, device 200 may restore the multi-button menuicon to its original size. In one implementation, the size of themulti-button menu icon may be reduced, for example, to approximately thesize of the group of application icons being displayed on the display.

User input to select an item associated with the identified quick-accessbutton may be detected (block 780). For example, device 200 may receiveuser input (e.g., another touch, a selection via the cursor, or aselection via a keypad and/or control button) to select a particularapplication icon from the currently displayed group of applicationicons. The user input to select the particular application icon maytrigger launching an application associated with the particularapplication icon and/or presenting information associated with theparticular application icon.

FIGS. 8, 9, and 10 provide illustrations of exemplary user input for aquick-access menu on a variety of devices. FIG. 8 provides anillustration of an exemplary implementation of user input for aquick-access menu on a device 800 with a touch-sensitive display.Referring to FIG. 8, device 800 may include housing 810 and atouch-sensitive display 820. Other components, such as control buttons,a microphone, connectivity ports, memory slots, and/or speakers may belocated on device 800, including, for example, on a rear or side panelof housing 810. Although FIG. 8 shows exemplary components of device800, in other implementations, device 800 may contain fewer, different,differently arranged, or additional components than depicted in FIG. 8.

Touch-sensitive display 820 may include a display screen integrated witha touch-sensitive overlay. In an exemplary implementation,touch-sensitive display 820 may include a capacitive touch overlay. Anobject having capacitance (e.g., a user's finger) may be placed on ornear display 820 to form a capacitance between the object and one ormore of the touch sensing points. The touch sensing points may be usedto determine touch coordinates (e.g., location) of the touch. The touchcoordinates may be associated with a portion of the display screenhaving corresponding coordinates, including coordinates for amulti-button menu icon. In other implementations, different touch screentechnologies may be used.

Touch-sensitive display 820 may include the ability to identify movementof an object as the object moves on the surface of touch-sensitivedisplay 820. As described above with respect to, for example, FIGS. 6Aand 6B, device 800 may display on touch-sensitive display 820 aquick-access menu arrangement that accepts user input to a multi-buttonmenu icon (e.g., multi-button menu icon 110). In the implementationshown in FIG. 8, multi-button menu icon 110 may be positioned in a lowercorner of display 820 to accommodate, for example, a predominantlyleft-handed user. In other implementations, multi-button menu icon 110may be positioned in other locations determined by the user. In theimplementation of FIG. 8, the touch on touch-sensitive display 820 maycorrespond to the activation of multi-button menu icon 110 andsimultaneous selection of a quick-access button to display a group ofapplication icons 130. In the implementation shown in FIG. 8,multi-button menu icon 110 may be enlarged upon activation to moreeasily and/or accurately accept touch input. As shown in FIG. 8, theenlargement of the multi-button menu icon 110 may crowd the presentationof adjacent application icons 130, but not so much as to completelyprevent a user's identification of the adjacent application icons 130.

FIG. 9 provides an illustration of an exemplary implementation of userinput for a quick-access menu on a device 900 with a touch panelseparate from a display. Device 900 may include housing 910, touch panel920, and display 930. Other components, such as control buttons, akeypad, a microphone, a camera, connectivity ports, memory slots, and/orspeakers, may be located on device 900, including, for example, on arear or side panel of housing 910. Although FIG. 9 shows exemplarycomponents of device 900, in other implementations, device 900 maycontain fewer, different, differently arranged, or additional componentsthan depicted in FIG. 9.

FIG. 9 illustrates touch panel 920 being separately located from display930 on housing 910. Touch panel 920 may include any resistive touchpanel technology or other technology providing the ability to register aset of touch coordinates. User input on touch panel 920 may beassociated with display 930 by, for example, movement and location of acursor 940. User input on touch panel 920 may be in the form of thetouch of nearly any object, such as a body part (e.g., a finger, asshown) or a pointing device (e.g., a stylus, pen, etc.).

Touch panel 920 may be operatively connected with display 930 to allowthe combination of touch panel 920 and display 930 to be used as aninput device. Touch panel 920 may include the ability to identifymovement of an object as the object moves on the surface of touch panel920. As described above with respect to, for example, FIGS. 6A and 6B,device 900 may display on display 930 a quick-access menu arrangement100 that accepts (via touch panel 920) user input to a multi-button menuicon (e.g., multi-button menu icon 110). In the implementation of FIG.9, the touch on touch panel 920 may correspond to the activation ofmulti-button menu icon 110 and simultaneous selection of a quick-accessbutton to display a group of application icons 130. Because cursor 940is used to select a quick-access button, a smaller amount of enlargementof multi-button menu icon 110 upon activation may be used than comparedto, for example, a touch screen display. Alternatively, enlargement ofmulti-button menu icon 110 upon activation be may be the same as that ofa touch screen display or enlargement may not be necessary.

FIG. 10 provides an illustration of an exemplary implementation of userinput for a quick-access menu on a device 1000 with a set of controlbuttons a display. Device 1000 may include housing 1010, control buttons1020, and display 1030. Other components, such as a keypad, amicrophone, a camera, connectivity ports, memory slots, and/or speakers,may be located on device 1000, including, for example, on a rear,sliding, or side panel of housing 1010. Although FIG. 10 shows exemplarycomponents of device 1000, in other implementations, device 1000 maycontain fewer, different, differently arranged, or additional componentsthan depicted in FIG. 10.

FIG. 10 illustrates control buttons 1020 being separately located fromdisplay 1030 on housing 1010. User input on control buttons 1020 may beassociated with display 1030 by, for example, toggling between defineduser input locations within a quick-access menu arrangement. Forexample, in one implementation, control buttons 1020 may include adedicated control button to activate multi-button menu icon 110. Onceactivated, a user may toggle between quick-access buttons withinmulti-button menu icon 110 by using, for example, a joystick ordirection pad associated with control buttons 1020. A particularapplication icon may be selected by deactivating multi-button menu icon110 (e.g., by pressing the dedicated control button) and togglingthrough the application icons 130 (e.g., by using a joystick ordirection pad) to the desired particular application icon 130. Becauseno touch-sensitive input is used to select a quick-access button, noenlargement of multi-button menu icon 110 upon activation may be needed.Alternatively, activation of multi-button menu icon 110 by a dedicatedcontrol button may cause enlargement of multi-button menu icon 110.

Systems and/or methods described herein may display, on a screen of acomputing device, a multi-button menu icon and a group of applicationicons associated with one of the buttons of the multi-button menu icon.User input may be received to activate the multi-button menu icon and toidentify a first button of the multi-button menu icon associated with alocation of the user input. A group of application icons associated withthe identified first button of the multi-button menu icon may bedisplayed. A second button of the multi-button menu icon may beidentified based on a changed location of the user input and a differentgroup of application icons associated with the identified second buttonmay be displayed. The multi-button menu icon may be deactivated uponremoval of the user input, allowing one of the application icons to beselected with a second user input.

The foregoing description of implementations provides illustration anddescription, but is not intended to be exhaustive or to limit theinvention to the precise form disclosed. Modifications and variationsare possible in light of the above teachings or may be acquired frompractice of the invention.

For example, while implementations have been described primarily in thecontext of a mobile device (such as a radiotelephone, a PCS terminal, ora PDA), in other implementations the systems and/or methods describedherein may be implemented on other computing devices such as a laptopcomputer, a personal computer, a tablet computer, an ultra-mobilepersonal computer, or a home gaming system.

As another example, while a multi-button menu icon has been generallypresented as having a three-by-three arrangement of buttons, otherbutton arrangements may be used. The multi-button icon may include, forexample, any N-by-N or N-by-M arrangement where N and M are both anumber greater than 1.

Also, while a series of blocks has been described with regard to FIG. 7,the order of the blocks may be modified in other implementations.Further, non-dependent blocks may be performed in parallel.

It will be apparent that aspects described herein may be implemented inmany different forms of software, firmware, and hardware in theimplementations illustrated in the figures. The actual software code orspecialized control hardware used to implement these aspects is notlimiting of the invention. Thus, the operation and behavior of theseaspects were described without reference to the specific softwarecode—it being understood that software and control hardware may bedesigned to implement these aspects based on the description herein.

Further, certain portions of the invention may be implemented as “logic”that performs one or more functions. This logic may include hardware,such as an application specific integrated circuit or a fieldprogrammable gate array, or a combination of hardware and software.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of the invention. In fact, many ofthese features may be combined in ways not specifically recited in theclaims and/or disclosed in the specification.

No element, act, or instruction used in the present application shouldbe construed as critical or essential to the invention unless explicitlydescribed as such. Also, as used herein, the article “a” is intended toinclude one or more items. Where only one item is intended, the term“one” or similar language is used. Further, the phrase “based on” isintended to mean “based, at least in part, on” unless explicitly statedotherwise.

What is claimed is:
 1. A computing device-implemented method comprising: displaying, on a screen of the computing device and prior to user activation of a menu icon, the menu icon and a first group of application icons, the menu icon including a plurality of buttons, each of the plurality of buttons being associated with a different group of application icons; receiving a user input to activate the menu icon; identifying, based on the received user input to activate the menu icon, a selection of a first button of the menu icon associated with a location of the user input; enlarging, based on the selection, the menu icon and each of the plurality of buttons, the selected first button being enlarged to a size larger than each of the other plurality of buttons; enlarging the display of the menu icon to overlap at least one of the application icons in the first group of application icons; displaying, on the screen of the computing device, a second group of application icons associated with the selected first button of the menu icon, the second group of application icons being different than the first group of application icons; identifying a selection of a second button of the menu icon associated with a changed location of the user input; and displaying, on the screen of the computing device, a third group of application icons associated with the selected second button of the menu icon, the third group of application icons being different than the first group of application icons, being different than the second group of application icons, and being independent of the second group of application icons.
 2. The computing device-implemented method of claim 1, further comprising: deactivating the menu icon upon detecting a removal of the user input; and detecting a second user input to select one of the application icons from the third group of application icons associated with the identified second button of the menu icon.
 3. The computing device-implemented method of claim 1, where the menu icon further comprises an indicator to display the identified second button of the menu icon.
 4. The computing device-implemented method of claim 1, where the user input to activate the menu icon is a touch on a touch sensitive display.
 5. The computing device-implemented method of claim 1, where the user input to activate the menu icon includes one of: selecting the menu icon using a cursor, or activating the menu icon using a button on the computing device.
 6. The computing device-implemented method of claim 1, where the menu icon includes an indicator to identify a button on the menu icon that is currently selected.
 7. The computing device-implemented method of claim 1, where the application icons are associated with one or more applications including: a telephone application, a text-messaging application, an email application, an instant messaging (IM) application, a calendar application, a multimedia messaging system (MMS) application, a short message service (SMS) application, an image viewing application, a camera application, an organizer, a video player, an audio application, or a Global Positioning System (GPS) application.
 8. The computing device-implemented method of claim 1, where the menu icon includes a three-by-three arrangement of buttons.
 9. The computing device-implemented method of claim 1, where the computing device comprises: a radiotelephone, a personal communications system (PCS) terminal, or a personal digital assistant (PDA).
 10. The computing device-implemented method of claim 1, where the computing device comprises: a laptop computer, a personal computer, a tablet computer, an ultra-mobile personal computer, a personal gaming system, or a Global Positioning System (GPS) unit.
 11. A device comprising: a memory to store a plurality of instructions; and a touch-sensitive display; and a processor to execute instructions in the memory to: display, on the touch-sensitive display and prior to user activation of a menu icon, the menu icon and a first group of application icons, the menu icon including a plurality of buttons, each of the plurality of buttons being associated with a different group of application icons; receive a touch on the menu icon displayed on the touch-sensitive display; activate the menu icon based on the touch; track a changing location of the touch; identify a selection of a button of the menu icon based on the changing location of the touch; enlarge, based on the selection, the menu icon and each of the plurality of buttons, the selected button being enlarged to a size larger than each of the other plurality of buttons; enlarge the display of the menu icon to overlap at least one of the application icons in the first group of application icons; and display, on the touch-sensitive display, a second group of application icons associated with the selected button of the menu icon, the second group of application icons being different than the first group of application icons and being independent of the first group of application icons.
 12. The device of claim 11, where the processor further executes instructions in the memory to: deactivate the menu icon upon removal of the touch; and detect a touch on one of the application icons from the second group of application icons associated with the selected button of the menu icon.
 13. The device of claim 12, where the touch on one of the application icons triggers one of: launching an application associated with the one of the application icons, or presenting information associated with the one of the application icons.
 14. The device of claim 11, where the device comprises: a radiotelephone, a personal communications system (PCS) terminal, a personal digital assistant (PDA), a laptop computer, a personal computer, a tablet computer, an ultra-mobile personal computer, a camera, a gaming system, or a Global Positioning System (GPS) unit.
 15. The device of claim 11, where the menu icon includes a N-by-N arrangement of buttons, where N is greater than
 1. 16. The device of claim 11, where the menu icon further comprises an indicator to display the group of application icons associated with a last-identified button of the menu icon.
 17. The device of claim 11, where the processor further executes instructions in the memory to: receive a user input to identify one or more application icons assigned to the second group of application icons associated with the selected button of the menu icon.
 18. The device of claim 11, where a location, on the touch-sensitive display, of the menu icon and the second group of application icons is determined by a user.
 19. A non-transitory computer-readable medium storing instructions, the instructions comprising: one or more instructions which, when executed by at least one processor, cause the at least one processor to: display, prior to user activation of a menu icon, the menu icon and a first group of application icons on a screen of a device, the menu icon including a plurality of buttons, each of the plurality of buttons being associated with a different group of application icons, and the first group of application icons being different than each of the different groups of application icons; receive a user input to activate the menu icon; identify, based on the received user input to activate the menu icon, a selection of a button of the menu icon based on a location of the user input; enlarge, based on the selection, the menu icon and each of the plurality of buttons, the selected button being enlarged to a size larger than each of the other plurality of buttons; enlarge the display of the menu icon to overlap at least one of the application icons in the first group of application icons; display, on the screen of the device, a second group of application icons, of the different group of application icons, associated with the selected button of the menu icon; track a changing location of the user input; identify another button of the menu icon based on the changing location of the user input; display a third group of application icons, of the different group of application icons, associated with the identified other button of the menu icon, the third group of application icons being different than the first group of application icons, being different than the second group of application icons, and being independent of the second group of application icons; and detect another user input to select one of the application icons from the group of application icons associated with the identified second button of the menu icon.
 20. The medium of claim 19, where the one or more instructions are further to: deactivate the menu icon upon removal of the user input.
 21. The medium of claim 19, where the menu icon further comprises: an indicator to display the identified second button of the menu icon, and an indicator to identify a button on the menu icon that is currently selected.
 22. The medium of claim 19, where the menu icon includes a N-by-N arrangement of buttons, where N is greater than
 1. 